Method and Apparatus for Managing Dual Registration with Multiple Networks in One or More Radio Communication Systems

ABSTRACT

A method and apparatus provides for establishing a communication connection between the network entity and the user equipment, while the user equipment has established and is maintaining an alternative communication connection with another network entity associated with a second one of the multiple networks. Flow management information is received from a shared common control element of the user equipment, which manages parallel user equipment activity including a flow of information between the user equipment and each of the multiple networks via the respective communication connections. The user equipment is communicated with in a manner which is consistent with the flow management information received from the shared common control element. The shared common control element includes one or more away patterns, that are each shared with a respective one of the first one and the second one of the multiple networks, where each of the one or more away patterns define periods of time during which the corresponding one of the first one and the second one of the multiple networks should avoid scheduling communications with the user equipment.

FIELD OF THE INVENTION

The present disclosure is directed to a method and apparatus formanaging dual registration in one or more radio communication systems,which include multiple networks, and more specifically for the managingof parallel user equipment activity relative to establishedcommunication connections between the user equipment and the multiplenetworks, where each network supports a different radio accesstechnology.

BACKGROUND OF THE INVENTION

Presently, user equipment, such as wireless communication devices,communicate with other communication devices using wireless signals,such as within a network environment that can include one or more cellswithin which various communication connections with the network andother devices operating within the network can be supported. Networkenvironments often involve one or more sets of standards, which eachdefine various aspects of any communication connection being made whenusing the corresponding standard within the network environment.

Examples of developing and/or existing standards include new radioaccess technology (NR), Long Term Evolution (LTE), Universal MobileTelecommunications Service (UMTS), Global System for MobileCommunication (GSM), and/or Enhanced Data GSM Environment (EDGE).

The manner in which information is handled and/or the types of entitieswithin the network available for handling the information can bedifferent in each type of network. Correspondingly, there may beinstances where a type of service or an application associated with aparticular wireless communication device will be better suited to aparticular one of multiple different network environments. Which networkis better suited may be different for different services or application.As such, there may be instances where it may be desirable for a wirelesscommunication device to maintain an active association with multiplenetworks, which can at least sometimes be referred to as dualregistration.

The present inventors have recognized, that in instances where dualregistration is utilized, it may be helpful for the multiplecommunication connections that are established with the multiplenetworks and the flow of information therethrough to be managed througha shared common control element, which can facilitate parallel userequipment activity in at least a first one and a second one of themultiple networks, as well as the corresponding routing of theinformation to be communicated as part of the parallel activity.

SUMMARY

Presently, user equipment, such as wireless communication devices,communicate with other communication devices using wireless signals.According to a possible embodiment, a method in a network entity of afirst one of multiple networks, each network supporting a differentradio access technology is provided. The method includes establishing acommunication connection between the network entity and the userequipment, while the user equipment has established and is maintainingan alternative communication connection with another network entityassociated with a second one of the multiple networks. Flow managementinformation is received from a shared common control element of the userequipment, which manages parallel user equipment activity including aflow of information between the user equipment and each of the multiplenetworks via the respective communication connections. The methodfurther includes communicating with the user equipment in a manner whichis consistent with the flow management information received from theshared common control element. The shared common control elementincludes one or more away patterns, that are each shared with arespective one of the first one and the second one of the multiplenetworks, where each of the one or more away patterns define periods oftime during which the corresponding one of the first one and the secondone of the multiple networks should avoid scheduling communications withthe user equipment.

According to another possible embodiment, a method in a network entityof a first one of multiple networks, each network supporting a differentradio access technology is provided. The method includes establishing acommunication connection between the network entity and the userequipment, while the user equipment has established and is maintainingan alternative communication connection with another network entityassociated with a second one of the multiple networks. Flow managementinformation is received from a shared common control element of the userequipment, which manages parallel user equipment activity including aflow of information between the user equipment and each of the multiplenetworks via the respective communication connections. The methodfurther includes communicating with the user equipment in a manner whichis consistent with the flow management information received from theshared common control element. When the sum of the power to be appliedto each of the transmitters during parallel user equipment activityexceeds a maximum allowed transmit power of the user equipment, themethod includes where the user equipment determines and applies a powerback off to be applied to at least one of the transmitters of the userequipment.

According to another possible embodiment, a network entity is provided.The network entity includes a transceiver that establishes acommunication connection between the network entity and the userequipment, while the user equipment has established and is maintainingan alternative communication connection with another network entityassociated with a second one of the multiple networks, where themultiple networks each support a different radio access technology, andthat receives flow management information from a shared common controlelement of the user equipment, which manages the parallel user equipmentactivity including a flow of information between the user equipment andeach of the multiple networks via the respective communicationconnections. The network entity further includes a controller thatmanages the flow of information communicated between the network entityand the user equipment via the transceiver of the network entity in amanner consistent with the flow management information that was receivedfrom the shared common control element of the user equipment. The sharedcommon control element includes one or more away patterns, that are eachshared with a respective one of the first one and the second one of themultiple networks, where each of the one or more away patterns defineperiods of time during which the corresponding one of the first one andthe second one of the multiple networks should avoid schedulingcommunications with the user equipment.

These and other objects, features, and advantages of the presentapplication are evident from the following description of one or morepreferred embodiments, with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overview of an exemplary network environment in which thepresent invention is adapted to operate;

FIG. 2 is a block diagram of an example of one possible form of couplingof the user equipment relative to multiple networks;

FIG. 3 is a block diagram of an example of a further possible form ofcoupling of the user equipment relative to multiple networks;

FIG. 4 is a message sequence diagram between a user equipment and anetwork for managing dual registration with multiple networks;

FIG. 5 is a message sequence diagram between a user equipment andmultiple networks for managing dual registration;

FIG. 6 is a flow diagram of a method in a user equipment for managingdual registration with multiple networks;

FIG. 7 is a flow diagram of a method in a network entity for managing acommunication connection with a user equipment as part of a dualregistration including multiple communication connections of the userequipment with multiple networks;

FIG. 8 is a flow diagram of a method in a user equipment for managingdual registration with multiple networks;

FIG. 9 is a flow diagram of a method in a network entity for supportingthe routing of messages received from a user equipment between multiplenetworks as part of a dual registration; and

FIG. 10 is an example block diagram of an apparatus according to apossible embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

While the present disclosure is susceptible of embodiment in variousforms, there is shown in the drawings and will hereinafter be describedpresently preferred embodiments with the understanding that the presentdisclosure is to be considered an exemplification of the invention andis not intended to limit the invention to the specific embodimentsillustrated.

Embodiments provide a method and apparatus for managing dualregistration in a radio communication system.

FIG. 1 is an example block diagram of a system 100 according to apossible embodiment. The system 100 can include a wireless communicationdevice 110, such as User Equipment (UE), a base station 120, such as anenhanced NodeB (eNB) or next generation NodeB (gNB), and a network 130.The wireless communication device 110 can be a wireless terminal, aportable wireless communication device, a smartphone, a cellulartelephone, a flip phone, a personal digital assistant, a personalcomputer, a selective call receiver, a tablet computer, a laptopcomputer, or any other device that is capable of sending and receivingcommunication signals on a wireless network.

The network 130 can include any type of network that is capable ofsending and receiving wireless communication signals. For example, thenetwork 130 can include a wireless communication network, a cellulartelephone network, a Time Division Multiple Access (TDMA)-based network,a Code Division Multiple Access (CDMA)-based network, an OrthogonalFrequency Division Multiple Access (OFDMA)-based network, a Long TermEvolution (LTE) network, a 5th generation (5G) network, a 3rd GenerationPartnership Project (3GPP)-based network, a satellite communicationsnetwork, a high altitude platform network, the Internet, and/or othercommunications networks.

A UE may benefit from availing itself of certain services bettersupported using the 5G System (e.g. NR/5GC) and certain other servicesbetter supported using the LTE Evolved Universal Terrestrial AccessNetwork (E-UTRAN)/Evolved Packet Core (EPC) system. To be able tosimultaneously use these services, each supported in a different system,is generally not readily supported today if both radios are3GPP-specified radio access technologies.

3GPP intends to support a mechanism allowing dual registration meaningthat the UE can register simultaneously in evolved packet system (EPS)and 5G system (5GS) as described e.g. in 3GPP TS 25301-v140 clause5.17.2.3. However, just dual registration itself may not allow parallelUE activity in both systems. The parallel UE activity in both systemsallows the UE to receive and to respond to Paging and perform mobilityRegistration/tracking area update (TAU) in each radio access technology(RAT) and possibly also actively use the packet data network (PDN)Connection and protocol data unit (PDU) Sessions established andactivated on the two Systems.

There are dual-radio solution e.g. for the combination of the followingradio access technologies (RATs): (1) for wireless local area network(WLAN) and 3GPP RAT and (2) for E-UTRA/LTE and code division multipleaccess (CDMA) 2000. However those mechanisms cannot be applied to3GPP-specific dual-radio RATs.

The existing solution may only rely on UE specific implementations. UEspecific implementations may not work however in the absence of aspecified solution specifying how the UE needs to ‘manage’ both RATs andbe active with single/dual receive (Rx)-transmit (Tx) capabilities. Forexample, it is not clear how a single Rx/Tx chain capable UE shallreceive and respond to paging in two different systems without apotential performance degradation in its active session in one of thesystems where it is in a radio resource control (RRC) Connected state.Similarly, it is not clear how a dual Rx/Tx chain capable UE shall splitits maximum UE transmit power to be able to support transmissions inboth of the systems, simultaneously, when the need arrives.

In the following description a “system” is defined as the whole networkincluding the Radio Access Network (RAN) based on 4th (E-UTRAN) or 5th(New RAT, NR) generation technologies and Core Network (EPC and 5GSrespectively for the 4th and 5th generation).

A UE can Register (also called Attach) itself to one of the systemsfirst. An RRC Idle state UE does this by first establishing an RRCConnection and then sends a non-access stratum (NAS) Registrationrequest message to a core network (CN) node. The relevant CN Node is amobility management entity (MME) and an access management function (AMF)for the EPC and 5GS respectively. The relevant CN Node may accept theUE's registration request (Attach Request) depending on the credentials(like subscription information present on the universal subscriberidentity module (USIM)) provided by the UE. After having attached to theSystem, the UE may initiate an establishment of some PDN Connection (in4^(th) generation) or PDU Session (in 5th generation) towards therelevant core network. Subsequent to the establishment of PDN Connectionor PDU Session the same maybe activated by establishing some DRBs (DataRadio Bearer) on the radio interface.

In one embodiment, the decision at the upper layers (e.g. NAS layer)works in the following way: A common NAS part (or one can call it upperNAS) decides if either or both NAS (LTE NAS and/or 5G NAS) need to be“used”. The said Upper or common NAS is a logical entity and could bepart of the access network discovery and selection function (ANDSF) orthe policy control function (PCF) in 5GS. This decision by the commonNAS part is based on services required and/or supported by the UE, UEdual registration and also radio capabilities, Network capability etc.Common NAS sits above both the NAS entities and works like an Upper NASprotocol. Access stratum supports the common/upper NAS by informing itas to what is supported/broadcasted by the network i.e. about networkcapabilities like support of Dual Registration andservice/Slice/application supported in the Radio and in the CoreNetwork(s). Whether (1) to initiate Dual Registration and (2) whether tosimultaneously use some connections to one system and other connectionto the other system (e.g. having simultaneous PDU Sessions to 5GS andPDN Connections to EPS) may depend on the following criteria: (A) accessstratum (AS) capabilities in the UE (single/dual radio, enhancements forusing multiple RATs), (B) capabilities in the RAN (e.g. support ofenhancements for using multiple RATs as specified in this invention)and/or (C) capabilities in the core network (CN) to support dualregistration (DR) mode and/or steering of connections among multiplesystems. Several examples are listed below:

-   -   (1) If the core network indicates to the UE that DR-mode is not        supported, then the UE does not initiate procedures for dual        registration, even though the UE may be capable of DR-mode and        at least some of the solutions below are supported.    -   (2) If the core network indicates support of DR-mode, but the        RAN (node) indicates non-support of enhancements for using        multiple RATs (e.g. some features as disclosed in this        invention), the UE may decide to perform DR but keeping all        connections (PDU Sessions or PDN Connections) in a single        system.    -   (3) If the AS layer indicates to the NAS layer (a) single-radio        capable (e.g. single Rx/Tx chain) and (b) support of        enhancements for using multiple RATs; and both RAN and CN        support such enhancements for using multiple RATs—then the NAS        layer can determine whether to perform DR and simultaneous use        of PDU Sessions and PDN Connections based on configuration or        subscription policies (e.g. as configured from Policy Control        Function, PCF, to the UE).

The eNB/gNB may broadcast relevant network capabilities in this regard.This can be done using a combined indication (combining capabilities ofboth RAN and CN) or individual capabilities could be separatelybroadcasted. The network capabilities could even be indicated on a perpublic land mobile network (PLMN) basis, in case of RAN sharing.

The UE may further proceed to register itself on the second/other Systemnext. As an example, in LTE/EPC the registration at the serving GPRSsupport node (SGSN)/mobile switching center (MSC) was done by the MME onbehalf of the UE for Combined Attached UEs. The Attach Accept messagefrom MME contains both 4th generation globally unique temporaryidentification (4G GUTI) and 3rd generation globally unique temporaryidentification (3G GUTI) or visitor location register (VLR) temporarymobile subscriber identity (TMSI). In 5GS a UE in Dual Registration(DR-mode) performs the registration at the AMF and the registration atthe MME by itself, i.e. UE-initiated registration. This DR-mode can beperformed even if the UE is single Rx/Tx capable; for example, afterregistering on the first system the UE initiates registration on thesecond system when it has transitioned to the RRC Idle mode of the firstsystem.

As one embodiment, this can be done in a number of ways. The UE mayindicate to the network RAN node that it is dual registration capable atsome point in time during or after the RRC Connection Establishment.Later, when the UE actually needs to register on the other system, itwill request the RAN Node to release the RRC Connection. The networkupon receiving the UE's request may reject the UE's request and UE shallthen remain in RRC Connected state as long as the network does notrelease the RRC Connection. In another possible variant, the UE mayautonomously start transitioning to RRC Idle after having sent to theRAN Node an indication indicating that the UE is subsequentlytransitioning to RRC Idle. In yet another possible variant, the UE mayautonomously start transitioning to RRC Idle without having sent to theRAN Node an indication indicating that the UE is subsequentlytransitioning to RRC Idle; in which case, the network upon noticing nouplink (UL) activity from the UE until a certain time duration willassume that the UE is no longer available i.e. has either met an RLF(Radio Link failure) condition and is therefore out of service, or, hastransitioned to RRC Idle autonomously. In yet another possible variant,the UE will request the RAN Node to transition the UE to RRC Inactivestate rather than releasing the RRC Connection itself. A UE in RRCInactive state would save the AS configuration/context until it returnsin the RRC Connected state of the said RAT. In the RRC Inactive state,this UE may tune away to another System and perform registration there.After having performed the registration, as soon as possible, the UEshall return to the said source RAT/System.

Where the present application refers to an idle state or an inactivestate, the teachings of the present application could generallycorrespond to either of the noted idle or inactive states, or both ofthe possible states.

If the UE is single Rx/Tx capable, the UE would miss the Paging in oneof the system and also not be able to perform mobility Registration/TAUin the RAT where it is away i.e. not tuned in currently. Following arethe possible enhancements that may be consistent with and/or realizablefrom the teachings of the present disclosure:

As one embodiment, the UE would determine one or more Gap or AwayPattern where it is not available in System 1 but is rather tuning tothe frequency of System 2 to be able to perform reception andtransmission there. The Away pattern(s) is then signaled to one of theRATs (like to eNB or gNB) where the UE is in an RRC Connected State. TheRAN node (like to eNB or gNB) may then attempt to avoid scheduling ofthe UE during the time periods indicated by the Away Pattern suggestedby the UE. The determination of the Away Pattern(s), suggested by the UEto the RAN Node, might itself account for the frequency retuning time.The RAN Node will also discount the periodic transmissions like physicaluplink control channel (PUCCH) or periodic buffer status report (BSR)reporting from the UE if they happen to collide with the Away Pattern.Any transmission counter towards such UL transmission may not beincremented. Alternatively, as an improvement of the embodiment, someparticular transmission like Scheduling Requests or particularactivation/deactivation MAC control elements (CEs) may be prioritizedover the Away Pattern and the UE may be tuned in on the frequency of theRAT where the UE is currently RRC Connected.

FIG. 2 illustrates a block diagram of an example of one possible form ofcoupling of the user equipment relative to multiple networks. Morespecifically, FIG. 2 highlights a user equipment (UE) radio resourcecontrol (RRC) coupled to a second system (System2), which from time totime can additionally and/or alternatively be tuned to a first system(System1). Such an arrangement is well suited to the use of a commoncontrol element, which can be used to manage the flow of informationbetween the user equipment and each of multiple networks via respectivecommunication connections.

One or more Away Patterns can be determined by the UE based on differenttime offset (say from system frame number zero (SFN #0), subframe #0),different Paging occasions, random access channel (RACH) opportunitiesetc. which may still fulfill the UE's requirement of reception and/ortransmission on the other RAT. In addition, there could be a minimumAway Pattern signaled which gives the network an indication on howperiodically the UE needs to be away. The away pattern(s) may bedetermined based on how frequently the UE needs to be active on theRAT1. The away pattern(s) may be re-determined from time to time whenthe UE's situation changes e.g. when the activity in the other RAT haschanged or the UE moves to a different frequency/Bank in either of theRATs etc. If a single Rx capable UE tunes to RAT1 only to listen toPaging then the Away pattern(s) will be one subframe (or time period)every Paging Occasion that the UE has for that system. The Pagingoccasion calculation is specified in 3GPP TS 36304-e30 or in future alsoin TS 38304. If the UE received a Paging message and needs to respondthen after tuning back in RAT2, the UE may need to convey another Awaypattern that allows the UE to send the Paging Response message in RAT1i.e. allows it to perform RACH Msg1, 2, 3 and 4 transmission as definedin 3GPP TS 36300-e00, transmission of NAS (Paging Response) message etc.If however, it is clear that the UE needs to stay longer in the RAT1e.g. to receive downlink (DL) data/transmit UL data, then the UE maysuggest RAT1 another Away Pattern enabling the UE to continue itsactivity in RAT2. The UE may also inform the RAN node 1 during an RRCConnection Establishment about any Dual Registration situation with the“other” RAT so that the RAN node 1 may expedite this UE's procedure andDL/UL data transfer. Of course, when the UE shares the Away Pattern withany RAT, the RAN Node may accept, modify (by changing the time periodavailability) or reject completely the UE's suggested away pattern. Incase of rejection, the UE may not be able to tune away from therejecting RAT. To be able to determine the Away Pattern, the UE needs tofirst autonomously tune in to RAT1 e.g. using discontinuous reception(DRX) sleep time and then synchronize to the RAN1 DL timeline. In doingso, the UE shall strive not to lose the synchronization with the sourceRAT e.g. by devoting one internal time clock to it or by similar means.The UE shall use the DL time difference of the source and the target RATto determine the Away Pattern such that the Paging occasion in RAT2coincides with the Away pattern indicated to RAT1 using RAT1's timeline.

In another embodiment, the UE may not be able to use an Away pattern butrather may stay on its current System. In doing so, the UE may be unableto perform registrations (mobility based and/or periodic) in the otherSystem. A dual Rx UE may still be able to receive the Paging messageitself by tuning/using one of its Rx Chain the frequency of the otherRAT; however, in absence of a dual transmitter, it may not be able tosend a Paging Response message without tuning away from the currentSystem. This embodiment makes it then possible to make the requiredtransmission (Paging Response and/or Registration) later when the UEtransitions to RRC Idle in the current RAT (of the current System) byreselecting to a cell of the other RAT (of the other System) and laterinitiating an RRC Connection Establishment there. Since this mighttypically delay the UE's UL transmission in the other System, the UEAccess Stratum shall inform the UE NAS of its inability and ability toperform the UL transmissions in the other System. The NAS shall save thepending NAS message and shall request the UE Access Stratum to go aheadwith the transmission to the UE Access Stratum indicating the ability toperform the UL transmission. This may however generally only be doneuntil a certain timer has expired, beyond which the UE may consideritself deregistered AND will then go ahead with a new/fresh registrationwith the other System. The timer itself may be UE implementationdependent or may be configurable by the network.

In a further embodiment, a dual Rx/Tx capable UE may tune itself to thefrequency of both of the Systems using the two available Rx/Tx chains.UE's total allowed transmission power P_(cmax) may need to becoordinated/split between the two RATs. According to one embodiment theUE could be configured by the network with a maximum transmission powerfor each RAT, i.e. P_(RAT1) and P_(RAT2). Power control is then furtherdone independently for each RAT. P_(RAT1)+P_(RAT2) may be smaller orequal to total UE transmit power, e.g. P_(cmax). Some additional powerback-off may be applied for determining the total UE maximum allowed TXpower, e.g. P_(cmax), for cases in which the UE is transmittingsimultaneously on two RATs. Such power restriction may be necessary froma regulation perspective in order to meet SAR (Specific Absorption Rate)requirements or out-of band emission requirements that may be affectedby inter-modulation products of the simultaneous radio transmissions. Inan alternative embodiment the UE may decide the power split between thetwo RATs. In other words, the UE may set the maximum transmission powerfor each RAT such that total UE transmission power is not exceeded. UEmay report the decided maximum transmission power for each RAT to thecorresponding network node. This allows an efficient scheduling ofuplink transmission within each RAT. In an alternative embodiment theuplink transmission power is dynamically shared between the twodifferent RATs. However, the required power levels for each transmissionmay exceed the allowed total UE transmitted power when a transmission inboth Systems needs to be made. Uplink and downlink transmission arescheduled independently in each RAT. Thus, for example, the UE may havetwo simultaneous uplink transmission scheduled, one by RAT1, the otherby RAT2, without one network entity/scheduling entity being aware of thescheduling information of the other network node/scheduling entity.Scheduling of PUCCH/PUSCH/PRACH/SRS of one link is not known to thenetwork entity of another link. According to one embodiment the UE mayprioritize uplink transmissions on one RAT over uplink transmission onthe other RAT in cases where the maximum total UE transmission power isexceeded. In some implementations the UE first determines thetransmission power for each RAT separately assuming that the other linkon the other RAT does not exist. Then the UE uses the determinedtransmission power for the prioritized RAT for uplink transmissions onthe prioritized RAT and uses the remaining power for the uplinktransmission on the other RAT. In cases where the determinedtransmission power for the other non-prioritized RAT exceeds theremaining power, the UE could perform power scaling for thenon-prioritized RAT. In another embodiment the priority of ULtransmissions/channel(s) between the two RATs is considered in thedynamic power sharing. For example in certain embodiments transmissionsof RRC messages, e.g. paging response message, higher reliability anddelay intolerant applications' data should be prioritized over otheruplink transmission channels/signals such that the transmission powerfor the RRC messages is not scaled. The UE may apportion itscapabilities among the two RATs based on one or more factors, such asdata rate, data volume, reliability, urgency etc. The apportionedcapabilities could include the physical layer and upper layercapabilities like Antenna Ports, layer one/two transmission/receptionbuffers, Band combinations supported, transmitted power etc. Theapportioned capabilities towards each RAT can be indicated to thecorresponding RATs when the UE transitions to an RRC Connected Stateand/or as part of a UE's ATTACH Request. To help indicate early a loweror scaled down capabilities like Tx power, some reserved Preamble ortime-frequency resources for PRACH transmissions can be used so that thereceiving RAN Node could be made aware of this and schedule the RACHMsg3 transmissions e.g. with lower frequency grant and/or with moreconservative MCS by providing a corresponding grant in RACH message 2(i.e. in Random Access Response).

When transmissions to both of the RATs need to take place such that atleast part of the transmission to the RATs can overlap then

-   -   (1) the power management related procedure may be performed in        the Physical layer such that the Physical layer based on the        destination RAT or Radio frequency carrier applies power scaling        and/or backoff while making transmission. In cases, when the        power is insufficient for at least one of the links and the        decision for power scaling needs to be made based on the        “content” of the transmission, the Physical layer will query        higher layers    -   (2) or, in cases, when the decision about prioritization        including go/no-go decision based on the “contents of the        transport block” needs to be made, then a UE entity sitting        above or at MAC needs to decide if the transmission intended for        one of the RATs is more important i.e. has higher priority than        the transmission intended for the other RAT. This prioritization        may affect only the power management, or the prioritization may        also be used in making a go/no-go or a pre-emption decision in        favor of transmission to one RAT.        The information about prioritization may be configured by the        network explicitly, such as using a Logical Channel        Prioritization (LCP value) or a similar new IE can be used or        the UE itself may judge which transmissions are more important        for it. For example, RRC signaling may be more important than        any data. Data from certain application may be more important        than data from other applications etc. The prioritization can        also be based on the quality of service class identifier—QCI/QOS        range.

A UE that needs to maintain two active sessions (PDN Connections and PDUSessions) with the two Systems in parallel for data transfer, shall needto establish and maintain two RRC Connections so that the NASConnections can also be maintained. NAS Connections (like S1-C and S1-Uin 4^(th) generation network and N2, N3 in 5^(th) generation network)allow the UE to maintain control and data connection with the respectivecore network elements. However, every dual Rx/Tx capable UE may not beable to establish and maintain two RRC/NAS Connections. The UE that arecapable of this may indicate their capability to the UE NAS, itself, andto the network. Based on this capability, the UE may decide to establishand maintain PDN Connections and PDU Sessions in parallel. Network maycontrol and coordinate UEs transmission, including power sharing or Awaypattern sharing as described earlier, in the two Systems based on thiscapability indication. The capability can be indicated to the network inone or more of the following messages and corresponding procedures e.g.as defined in 3GPP TS 36331-e30, 23401, 24301, 38331 etc.:

-   -   (1) RRC Connection Establishment or any subsequent RRC message    -   (2) In ATTACH Request message and/or in the RRC message carrying        NAS message like ULInformationTransfer    -   (3) In Location Registration messages like TAU (Tracking Area        Update) etc.

FIG. 3 illustrates a block diagram of an example of a further possibleform of coupling of the user equipment relative to multiple networks.More specifically, FIG. 3 highlights the user equipment (UE) registeringto two core networks (CNs) from the same radio access technology (RAT),such as via an associated evolved NodeB (eNB).

In another embodiment, such as an embodiment shown in the FIG. 3, the UEconnects to a RAT (e.g. an enhanced eNB) capable of connecting to both afourth (4th) and a fifth (5th) generation CNs. A UE in RRC Connected maythen get dual registered in two possible ways:

Accomplishing this with one CN Connection:

-   -   Accomplishing this with one CN Connection wherein eNB forwards        the NAS PDU (e.g. ATTACH request for the second CN) on the        existing CN interface e.g. N2 and then the first CN Node like        AMF determines that the NAS message is for MME e.g. based on        certain information, as described further, included by the UE        (in separate IEs) in the NAS PDU sent to the AMF. The AMF        forwards the NAS PDU (transparently) to the MME. The MME sends        back the reply (e.g. ATTACH Accept) to the UE using the same        route (via the same AMF) as shown in FIG. 4. Later on the MME        may initiate S1 establishment with the eNB and if some EPS        Bearer(s) need to be established then the eNB may configure        DRB(s) to the UE. The UE shall configure and maintain DRBs for        both Systems in parallel and in one option will use the security        keys and algorithm of the first System (fifth generation or 5G        in this example) to secure communication on the radio interface.        In another option the RAN may initiate the Security Mode        procedure (send Security Mode Command to the UE) and change the        UE's security algorithm and keys according to the UE capability        for the second System (4G in this example). In either case, the        NAS security will be based on the NAS SMS procedure from the        corresponding NAS entities (like MME or AMF) for their        corresponding NAS messages and procedures.

FIG. 4 illustrates a message sequence diagram between a user equipmentand a network for managing dual registration with multiple networks.More specifically, FIG. 4 highlights an example of non-access stratum(NAS) message exchanges between the user equipment (UE) and the corenetwork (CN) type 2 via the core network type 1, represented by anaccess management function (AMF) in this figure.

Here the DedicatedInfoNAS may contain information indicating to thefirst CN Type (AMF in above example) that the NAS PDU is destined to thesecond CN Type (MME in above example). The indication for MME could bean MME identity if the UE is already registered e.g.:

RegisteredMME ::= SEQUENCE { plmn-Identity PLMN-Identity OPTIONAL, mmegiBIT STRING (SIZE (16)) , mmec MMEC }Or, the indication for AMF could be just a Boolean flag indicating thatit (the NAS PDU) is destined for the other CN Type NAS entity (MME inthe above example). The example so far was such that the first CN TypeNAS entity is AMF and the second CN Type NAS entity is MME; if however,if the first CN Type NAS entity is MME and the second CN Type NAS entityis AMF, then the UE could include one (or more) of the following, if theUE is registered in 5G CN:

registeredAMF RegisteredAMF OPTIONAL, guami-Type ENUMERATED {native,OPTIONAL, mapped} ng-5G-S-TMSI-Value CHOICE { ng-5g-s-tmsi NG-5G-S-TMSI,ng-5g-s-tmsi-part2 BIT STRING (SIZE (9)) }Or, the indication for MME could be just a Boolean flag indicating thatit (the NAS PDU) is destined for the other CN Type NAS entity (AMF).

FIG. 5 illustrates a message sequence diagram between a user equipmentand multiple networks for managing dual registration. More specifically,FIG. 5 highlights a user equipment (UE) communicating with bothnon-access stratum core network (CN) types.

Accomplishing this with two CN connections:

-   -   While establishing the RRC Connection the UE must indicate to        the RAN node which CN it is intending to connect to. For this        purpose, the UE can include one of registeredAMF or        registeredAMF in the RRC Connection Setup Complete to the RAN        node. The RAN node establishes accordingly the NAS connection        i.e. N2 or S1 respectively. In the future, the UE may also need        to communicate with the second CN type and for this reason the        NAS PDU may be included and the eNB may need to identify which        CN node (MME or AMF) that a particular NAS message should be        forwarded to. This can be done in the following way:        -   In one embodiment, eNB selects the CN Connection (S1-C or            N2) based on indication from the UE. As one possibility,            both CN Connections are ‘active’ and an indication from the            UE (per NAS PDU contained in e.g. SRB2) could be per NAS            PDU. This indication could be either the address of MME or            AMF as shown below:

ULInformationTransfer message -- ASN1START ULInformationTransfer ::=SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulInformationTransferULInformationTransfer-IEs, spare3 NULL, spare2 NULL, spare1 NULL },criticalExtensionsFuture SEQUENCE { } } } ULInformationTransfer-IEs ::=SEQUENCE { dedicatedInfoNAS DedicatedInfoNAS OPTIONAL, CN_Type ::=CHOICE ( amf AMF-Address, mme MME-Address } lateNonCriticalExtensionOCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL }Alternatively, in the above structure instead of or in addition toAMF-Address or MME-Address the corresponding UE CN identity likeglobally unique AMF ID (guami) or S-temporary mobile subscriber identity(S-TMSI) could be carried.

Or, could be a Boolean where TRUE means CN1 and FALSE means CN2 whenboth the S1 and N2 links are already established.

ULInformationTransfer message -- ASN1START ULInformationTransfer ::=SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulInformationTransferULInformationTransfer-IEs, spare3 NULL, spare2 NULL, spare1 NULL },criticalExtensionsFuture SEQUENCE {} } } ULInformationTransfer-IEs ::=SEQUENCE { dedicatedInfoNAS DedicatedInfoNAS OPTIONAL, CN_TypeENUMERATED {AMF, MME} OPTIONAL, lateNonCriticalExtension OCTET STRINGOPTIONAL, nonCriticalExtension SEQUENCE { } OPTIONAL }

-   -   In one embodiment, where only one CN Connections may be ‘active’        at any point: An RRC message could be used to activate one of        the CN Connection (like either S1 or N2) and this CN Connection        could be used until the UE activates the other CN link. In        another variation, the UE NAS or the network side NAS could        trigger the NAS messages to start and stop a NAS session with        that CN Type. The RAN may also be informed and therefore at any        point of time, the RAN should know which NAS session is active        and will route the NAS PDUs both in UL and DL, accordingly.

Either or both CN may initiate data transmission by establishing andactivating PDN Connection/PDU Session for a UE. The eNB may initiateDRB(s) to serve the corresponding PDN Connection/PDU Session. The UE mayconfigure and maintain DRBs for both System in parallel and will use thesecurity keys and algorithm of the first System (5G in this example) tosecure communication on the radio interface. The NAS security will bebased on the NAS SMS procedure from the corresponding NAS entities (likeMME or AMF) for their corresponding NAS messages and procedures.

Deep Packet Inspection

In one embodiment, the RAN node looks inside of the NAS PDU and based onthe content of the PDU e.g. CN Type address, UE address or protocolmessage etc. will itself decide to which CN Type the NAS PDU isaddressed to and forward the packet to the same. However, until both S1and N2 links are established, the UE should continue to include CN Typeinformation explicitly in an RRC message (containing NAS PDU) to assistthe RAN node in routing the NAS PDU to the correct CN Type element, suchas to the MME or to the AMF.

FIG. 6 illustrates a flow diagram 600 of a method in a user equipmentfor managing dual registration with multiple networks. Morespecifically, a method in a user equipment for managing dualregistration in one or more radio communication systems is provided. Theone or more radio communication systems include multiple networks eachsupporting a different radio access technology. The method includesestablishing 602 a communication connection between the user equipmentand a first one of the multiple networks. The method further includesestablishing 604 a communication connection between the user equipmentand a second one of the multiple networks, while maintaining thecommunication connection between the user equipment and the first one ofthe multiple networks. A shared common control element in the userequipment manages 606 the flow of information between the user equipmentand each of the multiple networks via the respective communicationconnections, thereby allowing for parallel user equipment activity in atleast the first one and the second one of the multiple networks.

In some instances, the parallel user equipment activity can include oneor more of receiving and responding to paging; performing mobilityregistration or tracking area update in each radio access technology; oractively use the communication connections established on both the firstone and the second one of the multiple networks. In some of theseinstances, the communication connections being actively used on both thefirst one and the second one of the multiple networks can include packetdata connections or packet data sessions.

In some instances, the shared common control element can include amultilayer non access stratum having respective lower non access stratumassociated with a corresponding one of each of the multiple networks,and can have an upper common layer non access stratum which coordinatesthe parallel user equipment activity across the multiple networks.Additionally, the method can further include exchanging radiocommunication capabilities with one or more core network nodesassociated with the multiple networks of the radio communication system,and receiving from the upper common layer non access stratum anindication as to whether one or both of the lower non access stratumsassociated with each of the multiple networks should be used forsupporting concurrent access to the multiple networks. In some of theseinstances, as part of exchanging radio communication capabilities withthe one or more core network nodes, when one or more of the one or morecore network nodes indicates to the user equipment that a dualregistration mode is not supported, then the user equipment can refrainfrom initiating procedures for dual registration. In some of theseand/or other instances, as part of exchanging radio communicationcapabilities with the one or more core network nodes, when one or moreof the one or more core network nodes indicates to the user equipmentthat a dual registration mode is supported, but also indicates a lack ofsupport for using multiple types of radio access technology as part ofthe dual registration mode, then the user equipment can initiateprocedures for dual registration, while keeping all of the communicationconnections being established via one of the multiple networks. Furtheryet, as part of exchanging radio communication capabilities with the oneor more core network nodes, when each of the one or more core networknodes indicates to the user equipment support for multiple radio accesstechnologies, even if the user equipment is limited to being singleradio capable, then the upper layer non access stratum can make thedetermination as to whether to proceed with dual registration andparallel user equipment activity in at least the first one and thesecond one of the multiple networks. In support of dual registration andparallel user equipment activity in at least the first one and thesecond one of the multiple networks, when the user equipment is limitedto being single radio capable, the method in the user equipment canfurther include one or more of (1) requesting a release of a radioresource control connection associated with the communication connectionbetween the user equipment and the first one of the multiple networks,in order to establish the communication connection between the userequipment and the second one of the multiple networks; (2) autonomouslytransitioning to a radio resource control idle associated with thecommunication connection between the user equipment and the first one ofthe multiple networks, in order to establish the communicationconnection between the user equipment and the second one of the multiplenetworks; or (3) requesting a transition to an inactive state of theradio resource control connection associated with the communicationconnection between the user equipment and the first one of the multiplenetworks, in order to establish the communication connection between theuser equipment and the second one of the multiple networks.

In some instances, the shared common control element can include one ormore away patterns, that are each shared with a respective one of thefirst one and the second one of the multiple networks, where each of theone or more away patterns define periods of time during which thecorresponding one of the first one and the second one of the multiplenetworks should avoid scheduling communications with the user equipment.In some of these and/or other instances, the one or more away patternscan include defined time periods that take into account relativepredetermined priorities of the flow of information being conveyedbetween the user equipment and each of the multiple networks via therespective communication connections. Furthermore, as the relativepredetermined priority of the flow of information being conveyed betweenthe user equipment and each of the multiple networks via the respectivecommunication connections changes, the corresponding one or more awaypatterns can be adjusted. In some of these and/or other instances, eachof the one or more away patterns can be determined by the user equipmentbased on one or more of (1) different time offsets; (2) different pagingoccasions; or (3) random access channel opportunities.

In some instances, managing the flow of information between the userequipment and each of the multiple networks via the respectivecommunication connections by the shared common control element caninclude apportioning the capabilities of the user equipment between theestablished communication connections. In some of these and/or otherinstances, apportioning the capabilities of the user equipment betweenthe established communication connections can include determining theamount of power to apply to each transmitter, which is associated with arespective one of the established communication connections.Furthermore, when the sum of the power to be applied to each of thetransmitters during parallel user equipment activity exceeds a maximumallowed transmit power of the user equipment, the method can includedetermining and applying a power back off to be applied to at least oneof the transmitters. Further still, a non-prioritized communicationconnection as part of the parallel user equipment activity can bedetermined, and the power back off can be applied to at least thetransmitter associated with the non-prioritized communicationconnection. In some instances, apportioning the capabilities of the userequipment between the established communication connections can includeapportioning one or more of the antenna ports, the transmission orreception buffers, or supported band combinations. In some furtherinstances, the capabilities can be apportioned based on factorsincluding one or more of data rate, data volume, data reliability ordata urgency. Further yet, in some instances, the apportionedcapabilities can be indicated to one or more of the establishedcommunication connections, when the user equipment transitions to aconnected state relative to a particular communication connection, or aspart of an attach request.

FIG. 7 illustrates a flow diagram 700 of a method in a network entityfor managing a communication connection with a user equipment as part ofa dual registration including multiple communication connections of theuser equipment with multiple networks. More specifically, a method in anetwork entity of a first one of multiple networks is provided. Eachnetwork supports a different radio access technology. The methodincludes establishing 702 a communication connection between the networkentity and the user equipment, while the user equipment has establishedand is maintaining an alternative communication connection with anothernetwork entity associated with a second one of the multiple networks.The method further includes receiving 704 flow management informationfrom a shared common control element of the user equipment, whichmanages the parallel user equipment activity including a flow ofinformation between the user equipment and each of the multiple networksvia the respective communication connections. The method still furtherincludes communicating 706 with the user equipment in a manner which isconsistent with the flow management information received from the sharedcommon control element.

FIG. 8 illustrates a flow diagram 800 of a method in a user equipmentfor managing dual registration with multiple networks. Morespecifically, a method in a user equipment for managing dualregistration in one or more radio communication systems is provided. Theone or more radio communication systems include multiple networks, eachof the multiple networks supporting a different radio access technology.The method includes establishing 802 a communication connection betweenthe user equipment and a first one of the multiple networks. The methodfurther includes establishing 804 a communication connection between theuser equipment and a second one of the multiple networks via the firstone of the multiple networks, while maintaining the communicationconnection between the user equipment and the first one of the multiplenetworks. When routing one or more data packets to either of the firstone and the second one of the multiple networks via the respectivecommunication connection, the data packet is transmitted 806 to thefirst one of the multiple networks, where a determination is made as toan intended destination of the data packet, the data packet is thenrouted to the second one of the multiple networks, when the intendeddestination of the data packet is determined to be the second one of themultiple networks.

In some instances, the user equipment can couple to the multiplenetworks via a base transceiver station associated with the first one ofthe multiple networks. In some of these instances, the base transceiverstation can be coupled to a respective main signaling node of each ofthe first one and the second one of the multiple networks. Furthermore,the base transceiver station can be coupled to the main signaling nodeof the second one of the multiple networks via the main signaling nodeof the first one of the multiple networks. Still further, the basetransceiver station can be coupled to each respective one of the firstone and the second one of the multiple networks via a respective path ofcoupling, where the respective path of coupling is separate from themain signaling node of the other one of the first one and second one ofthe multiple networks. Further yet, the respective main signaling nodesof the first one and the second one of the multiple networks can includean access and mobility management function (AMF) and a mobilitymanagement entity (MME).

In some instances, an intended destination of a particular one of theone or more data packets can be determined by reading a registeredidentity value of a target entity from an associated one of the multiplenetworks, which is included as part of the data packet. In some of theseinstances, the registered identity value of a target entity can includean associated address value.

In some instances, a selectively set flag associated with a data packetcan identify an intended destination as being one of the multiplenetworks.

In some instances, information included inside the data packet can beinspected to identify the intended destination. In some of theseinstances, the information can be included inside the data packet thatis inspected includes one or more of a core network type address, userequipment address, or protocol message.

In some instances, a data radio bearer for each of the multiple networkscan be maintained in parallel.

In some instances, using the communication connection of a particularone of the multiple networks can include using security keys andalgorithms of the particular one of the multiple network being used.

FIG. 9 illustrates a flow diagram 900 of a method in a network entityfor supporting the routing of messages received from a user equipmentbetween multiple networks as part of a dual registration. Morespecifically, a method in a network entity of a first one of multiplenetworks is provided. Each network of the multiple networks supports adifferent radio access technology. The method includes establishing 902a communication connection between the network entity and the userequipment, while the user equipment has established and is maintainingan alternative communication connection with a second one of themultiple networks. Wherein when routing one or more data packets toeither of the first one and the second one of the multiple networks, thedata packet is received 904 by the network entity of the first one ofthe multiple networks, where a determination is made as to an intendeddestination of the data packet. The data packet is then routed to thesecond one of the multiple networks, when the intended destination ofthe data packet is determined by the network entity to be the second oneof the multiple networks.

It should be understood that, notwithstanding the particular steps asshown in the figures, a variety of additional or different steps can beperformed depending upon the embodiment, and one or more of theparticular steps can be rearranged, repeated or eliminated entirelydepending upon the embodiment. Also, some of the steps performed can berepeated on an ongoing or continuous basis simultaneously while othersteps are performed. Furthermore, different steps can be performed bydifferent elements or in a single element of the disclosed embodiments.

FIG. 10 is an example block diagram of an apparatus 1000, such as thewireless communication device 110, according to a possible embodiment.The apparatus 1000 can include a housing 1010, a controller 1020 withinthe housing 1010, audio input and output circuitry 1030 coupled to thecontroller 1020, a display 1040 coupled to the controller 1020, atransceiver 1050 coupled to the controller 1020, an antenna 1055 coupledto the transceiver 1050, a user interface 1060 coupled to the controller1020, a memory 1070 coupled to the controller 1020, and a networkinterface 1080 coupled to the controller 1020. The apparatus 1000 canperform the methods described in all the embodiments

The display 1040 can be a viewfinder, a liquid crystal display (LCD), alight emitting diode (LED) display, a plasma display, a projectiondisplay, a touch screen, or any other device that displays information.The transceiver 1050 can include a transmitter and/or a receiver. Theaudio input and output circuitry 1030 can include a microphone, aspeaker, a transducer, or any other audio input and output circuitry.The user interface 1060 can include a keypad, a keyboard, buttons, atouch pad, a joystick, a touch screen display, another additionaldisplay, or any other device useful for providing an interface between auser and an electronic device. The network interface 1080 can be aUniversal Serial Bus (USB) port, an Ethernet port, an infraredtransmitter/receiver, an IEEE 1394 port, a WLAN transceiver, or anyother interface that can connect an apparatus to a network, device, orcomputer and that can transmit and receive data communication signals.The memory 1070 can include a random access memory, a read only memory,an optical memory, a solid state memory, a flash memory, a removablememory, a hard drive, a cache, or any other memory that can be coupledto an apparatus.

The apparatus 1000 or the controller 1020 may implement any operatingsystem, such as Microsoft Windows®, UNIX®, or LINUX®, Android™, or anyother operating system. Apparatus operation software may be written inany programming language, such as C, C++, Java or Visual Basic, forexample. Apparatus software may also run on an application framework,such as, for example, a Java® framework, a .NET® framework, or any otherapplication framework. The software and/or the operating system may bestored in the memory 1070 or elsewhere on the apparatus 1000. Theapparatus 1000 or the controller 1020 may also use hardware to implementdisclosed operations. For example, the controller 1020 may be anyprogrammable processor. Disclosed embodiments may also be implemented ona general-purpose or a special purpose computer, a programmedmicroprocessor or microprocessor, peripheral integrated circuitelements, an application-specific integrated circuit or other integratedcircuits, hardware/electronic logic circuits, such as a discrete elementcircuit, a programmable logic device, such as a programmable logicarray, field programmable gate-array, or the like. In general, thecontroller 1020 may be any controller or processor device or devicescapable of operating an apparatus and implementing the disclosedembodiments. Some or all of the additional elements of the apparatus1000 can also perform some or all of the operations of the disclosedembodiments.

The method of this disclosure can be implemented on a programmedprocessor. However, the controllers, flowcharts, and modules may also beimplemented on a general purpose or special purpose computer, aprogrammed microprocessor or microcontroller and peripheral integratedcircuit elements, an integrated circuit, a hardware electronic or logiccircuit such as a discrete element circuit, a programmable logic device,or the like. In general, any device on which resides a finite statemachine capable of implementing the flowcharts shown in the figures maybe used to implement the processor functions of this disclosure.

While this disclosure has been described with specific embodimentsthereof, it is evident that many alternatives, modifications, andvariations will be apparent to those skilled in the art. For example,various components of the embodiments may be interchanged, added, orsubstituted in the other embodiments. Also, all of the elements of eachfigure are not necessary for operation of the disclosed embodiments. Forexample, one of ordinary skill in the art of the disclosed embodimentswould be enabled to make and use the teachings of the disclosure bysimply employing the elements of the independent claims. Accordingly,embodiments of the disclosure as set forth herein are intended to beillustrative, not limiting. Various changes may be made withoutdeparting from the spirit and scope of the disclosure.

In this document, relational terms such as “first,” “second,” and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. The phrase“at least one of,” “at least one selected from the group of,” or “atleast one selected from” followed by a list is defined to mean one,some, or all, but not necessarily all of, the elements in the list. Theterms “comprises,” “comprising,” “including,” or any other variationthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, article, or apparatus that comprises a list of elementsdoes not include only those elements but may include other elements notexpressly listed or inherent to such process, method, article, orapparatus. An element proceeded by “a,” “an,” or the like does not,without more constraints, preclude the existence of additional identicalelements in the process, method, article, or apparatus that comprisesthe element. Also, the term “another” is defined as at least a second ormore. The terms “including,” “having,” and the like, as used herein, aredefined as “comprising.” Furthermore, the background section is writtenas the inventor's own understanding of the context of some embodimentsat the time of filing and includes the inventor's own recognition of anyproblems with existing technologies and/or problems experienced in theinventor's own work.

What is claimed is:
 1. A method in a network entity of a first one ofmultiple networks, each network supporting a different radio accesstechnology, the method comprising: establishing a communicationconnection between the network entity and the user equipment, while theuser equipment has established and is maintaining an alternativecommunication connection with another network entity associated with asecond one of the multiple networks; receiving flow managementinformation from a shared common control element of the user equipment,which manages parallel user equipment activity including a flow ofinformation between the user equipment and each of the multiple networksvia the respective communication connections; and communicating with theuser equipment in a manner which is consistent with the flow managementinformation received from the shared common control element; and whereinthe shared common control element includes one or more away patterns,that are each shared with a respective one of the first one and thesecond one of the multiple networks, where each of the one or more awaypatterns define periods of time during which the corresponding one ofthe first one and the second one of the multiple networks should avoidscheduling communications with the user equipment.
 2. A method inaccordance with claim 1, wherein the parallel user equipment activityincludes one or more of receiving and responding to paging; performingmobility registration or tracking area update in each radio accesstechnology; or actively use the communication connections established onboth the first one and the second one of the multiple networks.
 3. Amethod in accordance with claim 2, wherein the communication connectionsbeing actively used on both the first one and the second one of themultiple networks include packet data connections or packet datasessions.
 4. A method in accordance with claim 1, wherein the sharedcommon control element includes a multilayer non access stratum havingrespective lower non access stratum associated with a corresponding oneof each of the multiple networks, and having an upper common layer nonaccess stratum which coordinates the parallel user equipment activityacross the multiple networks; the method further comprising: exchangingradio communication capabilities with the user equipment; receiving fromthe upper common layer non access stratum an indication as to whetherone or both of the lower non access stratums associated with each of themultiple networks should be used for supporting concurrent access to themultiple networks.
 5. A method in accordance with claim 4, wherein aspart of exchanging radio communication capabilities with the userequipment, when one or more of the one or more core network nodesindicates to the user equipment that a dual registration mode is notsupported, then the user equipment refrains from initiating proceduresfor dual registration.
 6. A method in accordance with claim 4, whereinas part of exchanging radio communication capabilities with the userequipment, when one or more of the one or more core network nodesindicates to the user equipment that a dual registration mode issupported, but also indicates a lack of support for using multiple typesof radio access technology as part of the dual registration mode, thenthe user equipment initiates procedures for dual registration, whilekeeping all of the communication connections being established via oneof the multiple networks.
 7. A method in accordance with claim 4,wherein as part of exchanging radio communication capabilities with theuser equipment, when each of the one or more core network nodesindicates to the user equipment support for multiple radio accesstechnologies, even if the user equipment is limited to being singleradio capable, then the upper layer non access stratum can make thedetermination as to whether to proceed with dual registration andparallel user equipment activity in at least the first one and thesecond one of the multiple networks.
 8. A method in accordance withclaim 7, wherein in support of dual registration and parallel userequipment activity in at least the first one and the second one of themultiple networks, when the user equipment is limited to being singleradio capable, the method in the network entity further comprises one ormore of (1) releasing of a radio resource control connection associatedwith the communication connection between the user equipment and thefirst one of the multiple networks, in response to a request receivedfrom the user equipment, in order to establish the communicationconnection between the user equipment and the second one of the multiplenetworks; (2) autonomously transitioning to a radio resource controlidle associated with the communication connection between the userequipment and the first one of the multiple networks, in order for theuser equipment to establish the communication connection between theuser equipment and the second one of the multiple networks; or (3)receiving a request a transition to an inactive state of the radioresource control connection associated with the communication connectionbetween the user equipment and the first one of the multiple networks,in order for the user equipment to establish the communicationconnection between the user equipment and the second one of the multiplenetworks.
 9. A method in accordance with claim 1, wherein the one ormore away patterns include defined time periods that take into accountrelative predetermined priorities of the flow of information beingconveyed between the user equipment and each of the multiple networksvia the respective communication connections.
 10. A method in accordancewith claim 9, wherein as the relative predetermined priority of the flowof information being conveyed between the user equipment and each of themultiple networks via the respective communication connections changes,the corresponding one or more away patterns can be adjusted.
 11. Amethod in accordance with claim 1, wherein each of the one or more awaypatterns are determined by the user equipment based on one or more of(1) different time offsets; (2) different paging occasions; or (3)random access channel opportunities.
 12. A method in a network entity ofa first one of multiple networks, each network supporting a differentradio access technology, the method comprising: establishing acommunication connection between the network entity and the userequipment, while the user equipment has established and is maintainingan alternative communication connection with another network entityassociated with a second one of the multiple networks; receiving flowmanagement information from a shared common control element of the userequipment, which manages parallel user equipment activity including aflow of information between the user equipment and each of the multiplenetworks via the respective communication connections; and communicatingwith the user equipment in a manner which is consistent with the flowmanagement information received from the shared common control element;and wherein when the sum of the power to be applied to each of thetransmitters during parallel user equipment activity exceeds a maximumallowed transmit power of the user equipment, the method includes wherethe user equipment determines and applies a power back off to be appliedto at least one of the transmitters of the user equipment.
 13. A methodin accordance with claim 12, wherein a non-prioritized communicationconnection as part of the parallel user equipment activity isdetermined, and the power back off is applied by the user equipment toat least the transmitter associated with the non-prioritizedcommunication connection.
 14. A method in accordance with claim 12,wherein apportioning the capabilities of the user equipment between theestablished communication connections includes apportioning one or moreof the antenna ports, the transmission or reception buffers, orsupported band combinations.
 15. A method in accordance with claim 12,wherein the capabilities are apportioned based on factors including oneor more of data rate, data volume, data reliability or data urgency. 16.A method in accordance with claim 12, wherein the apportionedcapabilities are indicated to one or more of the establishedcommunication connections, when the user equipment transitions to aconnected state relative to a particular communication connection, or aspart of an attach request.
 17. A network entity comprising: atransceiver that establishes a communication connection between thenetwork entity and the user equipment, while the user equipment hasestablished and is maintaining an alternative communication connectionwith another network entity associated with a second one of the multiplenetworks, where the multiple networks each support a different radioaccess technology, and that receives flow management information from ashared common control element of the user equipment, which manages theparallel user equipment activity including a flow of information betweenthe user equipment and each of the multiple networks via the respectivecommunication connections; and a controller that manages the flow ofinformation communicated between the network entity and the userequipment via the transceiver of the network entity in a mannerconsistent with the flow management information that was received fromthe shared common control element of the user equipment; and wherein theshared common control element includes one or more away patterns, thatare each shared with a respective one of the first one and the secondone of the multiple networks, where each of the one or more awaypatterns define periods of time during which the corresponding one ofthe first one and the second one of the multiple networks should avoidscheduling communications with the user equipment.
 18. A network entityin accordance with claim 17, wherein the shared common control elementof the user equipment includes a multilayer non access stratum havingrespective lower non access stratum associated with a corresponding oneof each of the multiple networks, and having an upper common layer nonaccess stratum which coordinates the parallel user equipment activityacross the multiple networks; and wherein radio communicationcapabilities are exchanged between the multilayer non access stratum andone or more core network nodes associated with the multiple networks ofthe radio communication system, and the upper common layer non accessstratum provides an indication as to whether one or both of the lowernon access stratums associated with each of the multiple networks shouldbe used for supporting concurrent access to the multiple networks.
 19. Anetwork entity in accordance with claim 17 wherein the shared commoncontrol element includes capability apportioning control circuitry foruse in support of the user equipment supporting dual transmitcapability, where the capability apportioning control circuitrydetermines the allocation of the available capabilities of the userequipment between each of the established communication connections.